Address the following comment on packages/features/auth/signup/handlers/calcomHandler.ts at line 34:

<comment>Utility functions for building a legacy request object (`createProxifiedObject`, `buildLegacyHeaders`, `buildLegacyCookies`, `buildLegacyRequest`) duplicate existing implementations. This logic already exists in `apps/web/lib/buildLegacyCtx.ts` in `createProxifiedObject()`, `buildLegacyHeaders()`, `buildLegacyCookies()`, and `buildLegacyRequest()` functions.</comment>

<file context>
@@ -31,6 +31,33 @@ import {
 
 const log = logger.getSubLogger({ prefix: [&quot;signupCalcomHandler&quot;] });
 
+type HeadersLike = { entries(): IterableIterator&lt;[string, string]&gt; };
+type CookiesLike = { getAll(): { name: string; value: string }[] };
+
</file context>

Address the following comment on packages/features/webhooks/components/EventTypeWebhookListItem.tsx at line 45:

<comment>Swapping the inline revalidateEventTypeEditPage call for props.onInvalidate breaks event-type page cache revalidation because the only caller never passes onInvalidate, so we lose the previously required revalidate step entirely.</comment>

<file context>
@@ -35,14 +34,15 @@ export default function EventTypeWebhookListItem(props: {
   const deleteWebhook = trpc.viewer.webhook.delete.useMutation({
     async onSuccess() {
-      if (webhook.eventTypeId) revalidateEventTypeEditPage(webhook.eventTypeId);
+      await props.onInvalidate?.();
       showToast(t(&quot;webhook_removed_successfully&quot;), &quot;success&quot;);
       await utils.viewer.webhook.getByViewer.invalidate();
</file context>

Address the following comment on packages/features/shell/user-dropdown/UserDropdown.tsx at line 41:

<comment>Defaulting isPlatformUser to false causes existing call sites (which don’t pass the new platformUserInfo prop) to hide the Platform menu entry for platform users, breaking that navigation path.</comment>

<file context>
@@ -34,10 +32,13 @@ declare global {
-export function UserDropdown({ small }: UserDropdownProps) {
-  const { isPlatformUser } = useGetUserAttributes();
+export function UserDropdown({ small, platformUserInfo }: UserDropdownProps) {
+  const isPlatformUser = platformUserInfo?.isPlatformUser ?? false;
   const { t } = useLocale();
   const { data: user, isPending } = useMeQuery();
</file context>

Address the following comment on packages/features/webhooks/pages/webhook-new-view.tsx at line 38:

<comment>Switching from a direct `revalidateWebhooksList()` call to `await onInvalidate?.();` drops cache revalidation when parents don’t pass the new prop. The only call site still omits `onInvalidate`, so the webhooks list no longer revalidates after creating a webhook.</comment>

<file context>
@@ -35,7 +35,7 @@ export const NewWebhookView = ({ webhooks, installedApps }: Props) =&gt; {
       showToast(t(&quot;webhook_created_successfully&quot;), &quot;success&quot;);
       await utils.viewer.webhook.list.invalidate();
-      revalidateWebhooksList();
+      await onInvalidate?.();
       router.push(&quot;/settings/developer/webhooks&quot;);
     },
</file context>

Address the following comment on packages/features/ee/teams/components/MemberInvitationModal.tsx at line 413:

<comment>If createInviteMutation.mutateAsync rejects, the ClipboardItem promise never settles and the copy action hangs—restore async handling so failures propagate instead of leaving the promise pending.</comment>

<file context>
@@ -410,14 +410,17 @@ export default function MemberInvitationModal(props: MemberInvitationModalProps)
                       if (typeof ClipboardItem !== &quot;undefined&quot;) {
                         const inviteLinkClipbardItem = new ClipboardItem({
-                          &quot;text/plain&quot;: new Promise(async (resolve) =&gt; {
+                          &quot;text/plain&quot;: new Promise((resolve) =&gt; {
                             // Instead of doing async work and then writing to clipboard, do async work in clipboard API itself
-                            const { inviteLink } = await createInviteMutation.mutateAsync({
</file context>

Address the following comment on packages/features/ee/platform/pages/settings/members.tsx at line 70:

<comment>This new fallback renders “Not a platform user” whenever the DI props are missing, but the existing call site still omits them. As a result the platform members page now shows only that string instead of the members table.</comment>

<file context>
@@ -32,12 +56,23 @@ const PlatformMembersView = (props: Omit&lt;UserListTableProps, &quot;facetedTeamValues&quot;
+  }
+
+  if (!isPlatformUser &amp;&amp; !NoPlatformPlanComponent) {
+    return &lt;div&gt;Not a platform user&lt;/div&gt;;
+  }
 
</file context>

Address the following comment on packages/features/eventtypes/components/DuplicateDialog.tsx at line 46:

<comment>Removing the revalidateEventTypesList call means the /event-types unstable_cache (revalidate:3600) is never busted after duplicating an event type, so the list can stay stale for up to an hour before showing the new entry. Please keep the path revalidation (e.g., via an injected onInvalidate callback) when this mutation succeeds.</comment>

<file context>
@@ -44,7 +43,7 @@ const DuplicateDialog = () =&gt; {
     data: { pageSlug, slug, ...defaultValues },
   } = useTypedQuery(querySchema);
-  const [searchTerm, setSearchTerm] = useState(&quot;&quot;);
+  const [searchTerm, _setSearchTerm] = useState(&quot;&quot;);
   const debouncedSearchTerm = useDebounce(searchTerm, 500);
 
</file context>

Address the following comment on packages/features/shell/user-dropdown/UserDropdown.tsx at line 41:

<comment>Existing call sites still render `&lt;UserDropdown /&gt;` without the new `platformUserInfo` prop, so this fallback forces `isPlatformUser` to false and hides the Platform navigation for real platform users. Please continue sourcing the value internally or update every caller in the same change.</comment>

<file context>
@@ -34,10 +32,13 @@ declare global {
-export function UserDropdown({ small }: UserDropdownProps) {
-  const { isPlatformUser } = useGetUserAttributes();
+export function UserDropdown({ small, platformUserInfo }: UserDropdownProps) {
+  const isPlatformUser = platformUserInfo?.isPlatformUser ?? false;
   const { t } = useLocale();
   const { data: user, isPending } = useMeQuery();
</file context>

Address the following comment on packages/features/ee/platform/pages/settings/members.tsx at line 70:

<comment>With the new dependency injection, this branch now executes immediately because the only call site still invokes PlatformMembersView without platformUserInfo or fallback components. isPlatformUser defaults to false, so the members page now renders this placeholder instead of the real table, regressing core functionality.</comment>

<file context>
@@ -32,12 +56,23 @@ const PlatformMembersView = (props: Omit&lt;UserListTableProps, &quot;facetedTeamValues&quot;
+  }
+
+  if (!isPlatformUser &amp;&amp; !NoPlatformPlanComponent) {
+    return &lt;div&gt;Not a platform user&lt;/div&gt;;
+  }
 
</file context>

Address the following comment on packages/features/users/components/UserTable/InviteMemberModal.tsx at line 22:

<comment>Switching to props-based platformUser data leaves `platformUser` undefined because no caller passes the new prop, so platform invites lose their `isPlatform` flag and can no longer follow the platform-specific permission path.</comment>

<file context>
@@ -6,17 +6,20 @@ import { useLocale } from &quot;@calcom/lib/hooks/useLocale&quot;;
 export function InviteMemberModal(props: Props) {
   const { data: session } = useSession();
-  const { data: platformUser } = usePlatformMe();
+  const platformUser = props.platformUserInfo;
   const utils = trpc.useUtils();
   const { t, i18n } = useLocale();
</file context>

Address the following comment on packages/features/ee/teams/components/MemberInvitationModal.tsx at line 413:

<comment>If createInviteMutation.mutateAsync rejects, this promise never settles, so navigator.clipboard.write hangs and the error is swallowed. Please propagate the rejection (e.g., restore the async executor or add a reject handler).</comment>

<file context>
@@ -410,14 +410,17 @@ export default function MemberInvitationModal(props: MemberInvitationModalProps)
                       if (typeof ClipboardItem !== &quot;undefined&quot;) {
                         const inviteLinkClipbardItem = new ClipboardItem({
-                          &quot;text/plain&quot;: new Promise(async (resolve) =&gt; {
+                          &quot;text/plain&quot;: new Promise((resolve) =&gt; {
                             // Instead of doing async work and then writing to clipboard, do async work in clipboard API itself
-                            const { inviteLink } = await createInviteMutation.mutateAsync({
</file context>

Address the following comment on packages/features/eventtypes/components/tabs/webhooks/EventWebhooksTab.tsx at line 27:

<comment>By swapping out `revalidateEventTypeEditPage` for an injected `onInvalidate` you removed the only cache revalidation call; because the mutation success handlers never invoke `onInvalidate?.()`, the event-type edit page stays stale after edits/creates. Please trigger the callback on success so the cache still revalidates.</comment>

<file context>
@@ -19,9 +19,13 @@ import { Button } from &quot;@calcom/ui/components/button&quot;;
+  eventType,
+  onInvalidate 
+}: Pick&lt;EventTypeSetupProps, &quot;eventType&quot;&gt; &amp; {
+  onInvalidate?: () =&gt; void | Promise&lt;void&gt;;
+}) =&gt; {
   const { t } = useLocale();
</file context>

Address the following comment on packages/features/webhooks/components/EventTypeWebhookListItem.tsx at line 45:

<comment>Replacing revalidateEventTypeEditPage with props.onInvalidate?.() means deleting/toggling an event-type webhook no longer revalidates the edit page cache, because no onInvalidate callback is wired yet. Users won’t see their changes for roughly an hour. Please retain the direct revalidation (or add a fallback) until the callback is actually provided.</comment>

<file context>
@@ -35,14 +34,15 @@ export default function EventTypeWebhookListItem(props: {
   const deleteWebhook = trpc.viewer.webhook.delete.useMutation({
     async onSuccess() {
-      if (webhook.eventTypeId) revalidateEventTypeEditPage(webhook.eventTypeId);
+      await props.onInvalidate?.();
       showToast(t(&quot;webhook_removed_successfully&quot;), &quot;success&quot;);
       await utils.viewer.webhook.getByViewer.invalidate();
</file context>

Address the following comment on packages/features/eventtypes/components/DuplicateDialog.tsx at line 74:

<comment>By removing the direct revalidateEventTypesList call and relying on an optional onInvalidate callback, this component no longer revalidates the event type list when duplicating. The only in-repo caller renders &lt;DuplicateDialog /&gt; without that prop, so new duplicates won’t surface until the cache times out.</comment>

<file context>
@@ -72,10 +71,10 @@ const DuplicateDialog = () =&gt; {
 
   const duplicateMutation = trpc.viewer.eventTypesHeavy.duplicate.useMutation({
     onSuccess: async ({ eventType }) =&gt; {
+      await onInvalidate?.();
       await router.replace(`/event-types/${eventType.id}`);
 
</file context>